👋 I see @tnull was un-assigned.
If you'd like another reviewer assignment, please click here.

No idea if there are any MSRV, or other considerations. Just wanted to see if it will work and how hard it will be.

No idea if there are any MSRV, or other considerations. Just wanted to see if it will work and how hard it will be.

It's mostly the same considerations as on #400, although we relaxed MSRV since: given that mismatching rusqlite versions in different crates render them completely incompatible, bumping rusqlite is an effort that needs to be coordinated across ~most/adjacent crates in the ecosystem. That means, at least check in with BDK, Cashu, Payjoin, and make sure everybody has a patch and realease ready short term, as otherwise users might get into a hairy situation if they're forced for other reasons to upgrade while other dependencies don't have a rusqlite-bumped release ready.

On top of that, note that due to the ensuing breakage, bumping rusqlite needs to ship as part of a major release (or minor pre-1.0) to follow SemVer rules. In some cases (BDK, for example) the next such release could be months away, making coordination across the 'rusqlite cabal' (to quote Calle) all the more necessary.

For reference, also see this recent PR bitcoindevkit/bdk#2002 on the BDK side which proposed to bump to yet-another-incompatible version.

TLDR: We should of course eventually bump the dependencies, but it requires more inter-crate coordiantion first.

Oh. I forgot about #440. No worries, closing for now, will stay as a reference.

I'll try barking at a different tree: rusqlite/rusqlite#1727

I'll try barking at a different tree: rusqlite/rusqlite#1727

Ah, yeah, it would be awesome if they started doing versioning!